@opentelemetry/context-async-hooks

What is @opentelemetry/context-async-hooks?

The @opentelemetry/context-async-hooks package is part of the OpenTelemetry project, which provides a set of APIs, libraries, agents, and instrumentation to create and manage telemetry data (metrics, logs, and traces) for cloud-native software. Specifically, this package leverages Node.js' async_hooks module to implement context propagation for asynchronous operations. This is crucial for tracing and logging in asynchronous applications, as it allows developers to maintain context across asynchronous boundaries.

What are @opentelemetry/context-async-hooks's main functionalities?

Context Management

This feature allows for the management of context across asynchronous operations. It uses the AsyncLocalStorage class to create a new context storage, run a function within this context, and retrieve values from this context later in the async flow.

const { AsyncLocalStorage } = require('@opentelemetry/context-async-hooks');
const asyncLocalStorage = new AsyncLocalStorage();

asyncLocalStorage.run(new Map(), () => {
  asyncLocalStorage.getStore().set('key', 'value');
  someAsyncOperation().then(() => {
    console.log(asyncLocalStorage.getStore().get('key')); // Outputs: 'value'
  });
});

Context Propagation

This feature demonstrates how to set up the AsyncLocalStorageContextManager to work with OpenTelemetry's API for global context propagation. This setup is essential for tracing asynchronous operations across different parts of an application.

const { propagation } = require('@opentelemetry/api');
const { AsyncLocalStorageContextManager } = require('@opentelemetry/context-async-hooks');

const contextManager = new AsyncLocalStorageContextManager();
propagation.setGlobalPropagator(contextManager);

// Now, the context is propagated across asynchronous calls automatically.

Other packages similar to @opentelemetry/context-async-hooks

cls-hooked

The cls-hooked package provides a similar functionality to @opentelemetry/context-async-hooks by using the async_hooks module to create context-like namespaces that are preserved across asynchronous calls. It differs in its API and is not specifically tailored for OpenTelemetry or tracing but can be used for general context propagation purposes.

async_hooks

While not a separate npm package, Node.js' built-in async_hooks module is the underlying technology that both @opentelemetry/context-async-hooks and cls-hooked rely on for tracking asynchronous operations. It provides the primitives for creating hooks that monitor the lifecycle of asynchronous operations, which can be used directly for custom context propagation implementations.

README

OpenTelemetry AsyncHooks-based Context Manager

This package provides async-hooks based context manager which is used internally by OpenTelemetry plugins to propagate specific context between function calls and async operations. It only targets NodeJS since async-hooks is only available there.

What is a ContextManager

The definition and why they exist is available on the readme of the context-base package.

Implementation in NodeJS

NodeJS has a specific API to track async context: async-hooks, it allows to track creation of new async operation and their respective parent. This package only handle storing a specific object for a given async hooks context.

Limitations

Even if the API is native to NodeJS, it doesn't cover all possible cases of context propagation but there is a big effort from the NodeJS team to fix those. That's why we generally advise to be on the latest LTS to benefit from performance and bug fixes.

There are known modules that break context propagation (some of them are listed there), so it's possible that the context manager doesn't work with them.

Prior arts

Context propagation is a big subject when talking about tracing in NodeJS, if you want more information about that here are some resources:

• https://www.npmjs.com/package/continuation-local-storage (which was the old way of doing context propagation)
• Datadog's own implementation for their Javascript tracer: here
• OpenTracing implementation: here
• Discussion about context propagation by the NodeJS diagnostics working group: here

Useful links

• For more information on OpenTelemetry, visit: https://opentelemetry.io/
• For more about OpenTelemetry JavaScript: https://github.com/open-telemetry/opentelemetry-js
• For help or feedback on this project, join us in GitHub Discussions

License

Apache 2.0 - See LICENSE for more information.

Changelog

0.23.0

:rocket: (Enhancement)

• opentelemetry-shim-opentracing
  • #2282 feat(shim-opentracing): update logging based on new spec (@vreynolds)
• opentelemetry-exporter-collector-grpc
  • #2304 feat: otlp-grpc exporter uses headers environment variables (@vreynolds)
• opentelemetry-propagator-b3
  • #2285 fix(propagator-b3): update extract to check for array (@jordanworner)
• opentelemetry-core, opentelemetry-instrumentation-fetch, opentelemetry-instrumentation-xml-http-request, opentelemetry-web
  • #2226 fix(xhr): make performance observer work with relative urls (@mhennoch)

:books: (Refine Doc)

• Other
  • #2306 chore: update the website getting started docs (@dyladan)
  • #2283 Module opentelemetry/instrumentation-grpc required (@pramodsreek)
• opentelemetry-sdk-node
  • #2300 chore(README): update link to BatchSpanProcessor in sdk node (@pragmaticivan)
• opentelemetry-exporter-jaeger, opentelemetry-exporter-zipkin, opentelemetry-sdk-node
  • #2290 fix: service.name resource attribute (@OmkarKirpan)
• opentelemetry-resources
  • #2289 docs(opentelemetry-resources): fix wrong sample code in readme (@alisabzevari)

:house: (Internal)

• opentelemetry-context-async-hooks, opentelemetry-context-zone-peer-dep, opentelemetry-web
  • #2247 feat: unify the signatures of bind and with (@Rauno56)
• Other
  • #2296 chore: do not upgrade backwards compatibility (@dyladan)
  • #2302 chore: use setup-node (@dyladan)

Committers: 9

• Ali Sabzevari (@alisabzevari)
• Daniel Dyla (@dyladan)
• Ivan Santos (@pragmaticivan)
• Jordan Worner (@jordanworner)
• MartenH (@mhennoch)
• Omkar Kirpan (@OmkarKirpan)
• Pramod (@pramodsreek)
• Rauno Viskus (@Rauno56)
• Vera Reynolds (@vreynolds)